[ACS-8960] Review and apply required inputs where possible #10554
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dominikiwanekhyland
requested review from
eromano,
popovicsandras and
DenysVuika
as code owners
|
@dominikiwanekhyland I see you added required inputs only for "content-services", "process-services-cloud" and "process-services". We have more libs here, for example "core". Can you add also some required fields for components in rest libs? |
|
@dominikiwanekhyland please remember to do the same for ACA, ADW and ACC. |
dominikiwanekhyland
force-pushed
the
ACS-8960-review-and-apply-required-inputs-where-possible
branch
from
86402c5 to
4e64787
Compare
|
AleksanderSklorz
approved these changes
Jan 17, 2025
MichalKinas
approved these changes
Jan 17, 2025
dominikiwanekhyland
deleted the
ACS-8960-review-and-apply-required-inputs-where-possible
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behaviour? (You can also link to an open issue here)
https://hyland.atlassian.net/browse/ACS-8960
What is the new behaviour?
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: